Explicitly import Vitest APIs instead of relying on globals #2931
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Kocal
commented
Jul 20, 2025
| */ | ||
|
|
||
| import '@testing-library/jest-dom'; | ||
| import '@testing-library/jest-dom/vitest'; |
There was a problem hiding this comment.
Needed, because @testing-library/jest-dom relied on global expect
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purely internal.
With Vitest, it is "recommended" to not use globals (disabled by default) and instead relying on explicit
import.Even if it means to add more code in the codebase, “Explicit is better than implicit”, and global types definitions can be a mess sometimes.